SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 33870: SAS® Stored Process Server might stop responding if METASERVER or METAPORT options are used

DetailsAboutRate It

When running a SAS® Stored Process on the SAS® Stored Process Server or the SAS Pooled Workspace Server, the METASERVER and METAPORT options should not be used on an OPTIONS statement. If you use these options, the SAS Stored Process Server might stop responding.

There is no need to specify these options in a SAS Stored Process because the SAS Stored Process Server is started with configuration files that already specify METASERVER and METAPORT. In addition, each SAS Stored Process request that is run has METAUSER and METAPASS set automatically to the client user identity using SAS Token authentication.

If you use the METASERVER and METAPORT options and reference a SAS® Metadata Server that is different than the one that the SAS Stored Process Server is using, this will cause the SAS Stored Process Server to stop responding. You will receive the following error message in your Web browser when you attempt to execute the SAS Stored Process:

   Stored Process Error
   Unable to execute stored process
   User is not authorized to access stored process.
 

Or, you might receive the following error message:

New client connection (29) rejected from server port 8611 
for user some_userid@!*(generatedpassworddomain)*!.

For example, the following code would encounter the problem:

    /* Do not use this approach */
  options metaserver     = "another.server.name"
          metaport       =  8561
          metarepository = "Foundation"
          metauser       = "xxxxxx\sasdemo"
          metapass       = "xxxxxx";

  %stpbegin;

    proc print data=sashelp.class;
    run;

  %stpend;  

If you need to connect to the current SAS Metadata Server using a different identity, you can specify METAUSER and METAPASS on an options statement. This will set the option values for the duration of the request or until they are changed again. For example:

options metauser = "xxxxxx\sasdemo" metapass = "xxxxxx";

Another, usually better, way to obtain a SAS Metadata Server connection under a different identity is to use the SAS® procedure syntax or LIBNAME syntax to specify the user and password (or even specify the METASERVER and METAPORT options). SAS procedure or LIBNAME syntax only uses the values for the connection required by the procedure or LIBNAME instead of affecting the entire request. Leaving them off the procedure or LIBNAME enables the procedure or LIBNAME to use the default connection or whatever values were set using the options statement.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS Integration Technologiesz/OS9.2 TS2M09.3 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.2 TS2M09.3 TS1M0
Microsoft Windows XP 64-bit Edition9.2 TS2M09.3 TS1M0
Microsoft® Windows® for x649.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Standard Edition9.2 TS2M09.3 TS1M0
Microsoft Windows XP Professional9.2 TS2M09.3 TS1M0
Windows Vista9.2 TS2M09.3 TS1M0
64-bit Enabled AIX9.2 TS2M09.3 TS1M0
64-bit Enabled HP-UX9.2 TS2M09.3 TS1M0
64-bit Enabled Solaris9.2 TS2M09.3 TS1M0
HP-UX IPF9.2 TS2M09.3 TS1M0
Linux9.2 TS2M09.3 TS1M0
Linux for x649.2 TS2M09.3 TS1M0
OpenVMS on HP Integrity9.2 TS2M09.3 TS1M0
Solaris for x649.2 TS2M09.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.